# Issue Report

**Date:** These tests were conducted from 1500PST to 1815PST on September 24th. 

## Observations

1. We were collect for an hour or so, changing little on the GUI when we noticed HEAD 1 had stopped scanning without a stop request.
2. Head 1 comms indicators were good, and diagnostics seemed like metrics were coming in. 
3. Repeated start stops of the software did not get scanning iniated from Head 1. Diagnostics shows no scan rate and raw free percent on head 1 was 99%. On diagnostics, packets were arriving still from Head 1. 
4. We restarted the GUI and Head 1 comms were still good but still had the same behavior. 
5. Logs indicated that after startup, Head 1 was stopping operation without a stop request or logged reason why. Below is a snippet of the log where this happened. 
	20200924::225540: Head 1: Stopping Scan Operation
6. Looking forward in the log you will see the diagnostic data that we witnessed while troubleshooting. 
7. We were able to resolve the problem by cycling power to the subsea electronics. 
8. Most perplexing there are no data logs from this time period we witnessed this happening. 

## Errata 

* When downloading the logs today for this incident, I also lost GUI comms to Head 1 again, I was not trying to scan, but in fact replay to find the bad file. I confirmed the Head 1 PC had remote desktop, GUI restarts did not fix it, and by restarting the service in firedaemon I got comms back in the GUI. Not sure if the data replay caused some hiccup, but worth mentioning.

* I would like to report a bug in the new feature that allows us to change power level while scanning. We appreciate this new function greatly. When a user clicks "CFG" and changes the dropdowns for power and then activates it with the "Apply Laser Power Now", the function succeeds and power is changed during that scan. However, if a user then closes that dialog with a click of the red "x" and not by hitting "OK", the "Sensor Parameters" pane does not reflect the current laser powers for the head. Furthermore, we are concerned this is a safety issue because you could be scanning in an non-eye-safe mode, use the new activation feature to move into an eyesafe mode, and hit the red "x", leaving non-eye-safe values in the sensor parameters window. On the next stop/start, you would then be unexpectedly in a non-eye-safe mode. Another bad scenario is that you could move from eye-safe to non-eye-safe modes through the instant activation, but leave the main GUI telling you that the mode is eyesafe.

